Incident Classes

Incident classes are categories used to organize sets of similar incidents, for example, Natural Disasters or Man-Made Incidents. When incident types and subTypes are created, you must specify the incident class they belong to.

Incident classes are also used to assign User Defined Fields to an incident, allowing custom fields to be defined for a certain class of incidents.

To open the Incident Classes page:

  1. Open the Administration Menu page.

  2. Under the INCIDENT ADMIN heading, click Incident Classes.

ClosedAdd an Incident Class

Adding an incident class allows you to define an grouping for incident types, subTypes, and UDFs. To add an incident class:

  1. In the Add Incident Class field, enter a name to describe the type of incident in the class.

    Incident class names must be unique. If you attempt to add an incident class that already exists, an error message will appear. The system does not consider incident class names that are differentiated only by character case to be unique. For example, if you create an incident class named "My Class", creating an incident class named "my class" is not allowed.

  2. Click ADD.

    A dialog box opens asking you to confirm your choice.

  3. Click OK.

ClosedEdit an Incident Class

Once you have created an incident class, you can further define it or edit it. To edit an incident class:

  1. In the Incident Class field, select the incident class to edit.

  2. To change the display order, enter a value in the Tab Order field.

    The Tab Order indicates the position, in menus, where this value will be listed. Lower numbered values are displayed toward the top of the list. Values will the same tab order will be sorted alphabetically.

  3. To change the name of the incident class, enter a value in the Rename field.

    All historical information will reflect the new value.

    Incident class names must be unique. If you attempt to rename an incident class to a name that already exists, an error message will appear. The system does not consider incident class names that are differentiated only by character case to be unique. For example, if the incident class "My Class" exists, renaming an incident class "my class" is not allowed.

  4. To change the status, select a value from the Status field.

    Incident classes with a status of Inactive are not displayed to users. However, inactivating an incident class does not affect the existing incidents that utilize it.

  5. In the Display Description I field, select Yes to include a Description I field on the Create Incident page when incidents belonging to this class are created. This field is intended to allow a user to enter the events that resulted in the incident.

  6. In the Display Description II field, select Yes to include a Description II field on the Create Incident page when incidents belonging to this class are created. This field is intended to allow a user to enter the corrective or preventive measures that were taken.

  7. In the Display Description III field, select Yes to include a Description III field on the Create Incident page when incidents belonging to this class are created. This field is intended to allow a user to enter information about the impact of the incident.

  8. In the Display Root Cause field, select Yes to include a Root Cause Investigation field on the Create Incident page when incidents belonging to this class are created. This field is intended to allow a user to enter the root cause of the incident.

  9. Click UPDATE.

ClosedDelete an Incident Class

Incident classes that have not been used can be deleted from the system.

Incident classes that have been used cannot be deleted, but they can be inactivated to prevent users from accessing them.

To delete an incident class:

  1. In the Incident Class field, select the incident class to delete.

  2. Click Delete.

    A dialog box opens asking you to confirm your choice.

  3. Click OK.

Accruent logo in white text.

© Copyright Accruent 2025Privacy PolicyTerms of UseLegal